-
Notifications
You must be signed in to change notification settings - Fork 1.4k
chore: throw error when importing core twice #7784
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: build/v2
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 4fc27e6 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
694fb2e
to
80fa09c
Compare
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
the reason playwright errored and now the cli tests that both run vite in ssr server mode which loads vite config with uses qwik-router vite plugin, which imports qwik core, and then the preview server runs in-process with its own qwik core copy. So it's actually a bug in our bundling! |
this should make it easier to detect build misconfigurations
80fa09c
to
372c9da
Compare
still gets core via dev server
- remove separate dev-server which duplicated route processing logic, instead use node adapter - watch routes for changes and reload when needed - make route imports always dynamic (optionally static). This limits the amount of code to load when not all paths are visited, and reduces startup time. - remove .testing condition on double import, the reason was the dev-server importing core separately from the test code Still missing: - transformindexhtml handling - entry.ts support - serviceworker support
cef66cb
to
24463c5
Compare
24463c5
to
dc4560b
Compare
4743ea1
to
4fc27e6
Compare
v2 version of #7109 with vendorRoots removal
also features reworking the router build so it doesn't import core
TODO: remove vite-dev-server from qwik